Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bc4bf2b8a1ab78ae1baad33fdb7e2d07a3120d499e91a3c4f2128bed5d18b819

Tx prefix hash: b015b48a64817f38b39f5ad90aa68241630bfee14fcacfac6b7ef327cbab9313
Tx public key: a0d66f578e146fc6c8cca94dc8a7318df1400dd837353e1ee71c4c1a709c72bf
Timestamp: 1703860661 Timestamp [UCT]: 2023-12-29 14:37:41 Age [y:d:h:m:s]: 01:305:12:08:21
Block: 923748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477175 RingCT/type: yes/0
Extra: 01a0d66f578e146fc6c8cca94dc8a7318df1400dd837353e1ee71c4c1a709c72bf0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4efa41131a7eee3a0f21e9e3bf3fb812b2717664ea6839a295092a9310cb6a16 0.600000000000 1381484 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 923758, "vin": [ { "gen": { "height": 923748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4efa41131a7eee3a0f21e9e3bf3fb812b2717664ea6839a295092a9310cb6a16" } } ], "extra": [ 1, 160, 214, 111, 87, 142, 20, 111, 198, 200, 204, 169, 77, 200, 167, 49, 141, 241, 64, 13, 216, 55, 53, 62, 30, 231, 28, 76, 26, 112, 156, 114, 191, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8