Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1745b77b5f2f0c9e3d78a0bc197214789db7b0d018c7b74541b05530e298b1

Tx prefix hash: 2240bb080e11ca7e3ffb5e6ea067b85332d04165a1770de4e2d9850b799165da
Tx public key: abf3d706b0810be0d7edbe8ae54eaa45363ed5a9fc54a277155519d1c66ca8ac
Timestamp: 1585550784 Timestamp [UCT]: 2020-03-30 06:46:24 Age [y:d:h:m:s]: 04:307:21:24:05
Block: 89892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118936 RingCT/type: yes/0
Extra: 01abf3d706b0810be0d7edbe8ae54eaa45363ed5a9fc54a277155519d1c66ca8ac02110000003e39be35fb000000000000000000

1 output(s) for total of 309.137196092000 dcy

stealth address amount amount idx
00: f5b7bc53d9eba05d9fb202834002441232148634233cf3385cc9782a2a171565 309.137196092000 161090 of 0

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": 89902, "vin": [ { "gen": { "height": 89892 } } ], "vout": [ { "amount": 309137196092, "target": { "key": "f5b7bc53d9eba05d9fb202834002441232148634233cf3385cc9782a2a171565" } } ], "extra": [ 1, 171, 243, 215, 6, 176, 129, 11, 224, 215, 237, 190, 138, 229, 78, 170, 69, 54, 62, 213, 169, 252, 84, 162, 119, 21, 85, 25, 209, 198, 108, 168, 172, 2, 17, 0, 0, 0, 62, 57, 190, 53, 251, 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