Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b2628cab9f6678da27c1a282d0f02b57ffe5231f6a36a1fe46c045cfc5991f2

Tx prefix hash: 0125694b69401d39e26dc90df97345af6bad6ad39fbf871a74a251108db18e84
Tx public key: 5ed3bc7dce7c68e79e2b5080fc50d0c2de16ffacd83601ba30a21cf997951f95
Timestamp: 1721509061 Timestamp [UCT]: 2024-07-20 20:57:41 Age [y:d:h:m:s]: 01:108:16:01:56
Block: 1070061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336154 RingCT/type: yes/0
Extra: 015ed3bc7dce7c68e79e2b5080fc50d0c2de16ffacd83601ba30a21cf997951f95021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b163fea45e18d4344a2c2e3d5d233dd582f94aae55b5f17c89ce9f0dbea91b6 0.600000000000 1541740 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": 1070071, "vin": [ { "gen": { "height": 1070061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b163fea45e18d4344a2c2e3d5d233dd582f94aae55b5f17c89ce9f0dbea91b6" } } ], "extra": [ 1, 94, 211, 188, 125, 206, 124, 104, 231, 158, 43, 80, 128, 252, 80, 208, 194, 222, 22, 255, 172, 216, 54, 1, 186, 48, 162, 28, 249, 151, 149, 31, 149, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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