Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be557519ab285ace431ce65c401c48a86e0d1b74bd9f57b618b0e3e4fc8709c

Tx prefix hash: b3f3f284df8e7be2b21df3590d8288c949426e08bd42d949a1c9a03a014e82eb
Tx public key: 6dc70024038ef862f6b53bf4be01f7463f771a5ebd12b4d2088b96352c3dbfaa
Timestamp: 1707106571 Timestamp [UCT]: 2024-02-05 04:16:11 Age [y:d:h:m:s]: 01:053:02:36:13
Block: 950648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299016 RingCT/type: yes/0
Extra: 016dc70024038ef862f6b53bf4be01f7463f771a5ebd12b4d2088b96352c3dbfaa02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbb93e51917461184757921fc888bef7d86f585d76459ce3761414c6ae7c523 0.600000000000 1409298 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": 950658, "vin": [ { "gen": { "height": 950648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbb93e51917461184757921fc888bef7d86f585d76459ce3761414c6ae7c523" } } ], "extra": [ 1, 109, 199, 0, 36, 3, 142, 248, 98, 246, 181, 59, 244, 190, 1, 247, 70, 63, 119, 26, 94, 189, 18, 180, 210, 8, 139, 150, 53, 44, 61, 191, 170, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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