Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e194e3352b5ab1fe04ba4d985bbf249a1f90e51f9c49f5ec90c38802087c86

Tx prefix hash: 52b2f4ceec9e711b12a9a1fff1d525e347fff1b1d88090bf55b3b6d602b102b4
Tx public key: d6fce299902fa954a7e948f93f24aaf90fd1ddb4d6ce14498905a62da77e0933
Timestamp: 1696984854 Timestamp [UCT]: 2023-10-11 00:40:54 Age [y:d:h:m:s]: 01:138:20:32:04
Block: 866960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360242 RingCT/type: yes/0
Extra: 01d6fce299902fa954a7e948f93f24aaf90fd1ddb4d6ce14498905a62da77e093302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.823003457000 dcy

stealth address amount amount idx
00: 0a202fd730db22b94df62119c458e14a436a1618eba8e12b7367d945e7bd07b8 0.823003457000 1321600 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": 866970, "vin": [ { "gen": { "height": 866960 } } ], "vout": [ { "amount": 823003457, "target": { "key": "0a202fd730db22b94df62119c458e14a436a1618eba8e12b7367d945e7bd07b8" } } ], "extra": [ 1, 214, 252, 226, 153, 144, 47, 169, 84, 167, 233, 72, 249, 63, 36, 170, 249, 15, 209, 221, 180, 214, 206, 20, 73, 137, 5, 166, 45, 167, 126, 9, 51, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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