Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a9b40e16d7c6209ae996af56d45e9f68aaa3760c29e23d5e4c7838eb99bbbf6

Tx prefix hash: d34252a7502ecdcbd8856c7c04cb9a36af3aacbcc734eb89bbd763152e0e066e
Tx public key: 5c45f0f4810bd5733028a68a978af2061c9db45884ced0f241fb74cf8d239483
Timestamp: 1716007593 Timestamp [UCT]: 2024-05-18 04:46:33 Age [y:d:h:m:s]: 00:171:00:17:21
Block: 1024454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122405 RingCT/type: yes/0
Extra: 015c45f0f4810bd5733028a68a978af2061c9db45884ced0f241fb74cf8d23948302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c467acb4214bef78e2f16625e2c74f53dce627b5f695c2aa4b759bcc08e5eb9b 0.600000000000 1490219 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": 1024464, "vin": [ { "gen": { "height": 1024454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c467acb4214bef78e2f16625e2c74f53dce627b5f695c2aa4b759bcc08e5eb9b" } } ], "extra": [ 1, 92, 69, 240, 244, 129, 11, 213, 115, 48, 40, 166, 138, 151, 138, 242, 6, 28, 157, 180, 88, 132, 206, 208, 242, 65, 251, 116, 207, 141, 35, 148, 131, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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