Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c410a506375e8f7362fec2fd149b934cbcc951ebc948afb2f7481cdacdba75

Tx prefix hash: d2aebbcf7372fe32fe3d209c14fc7dc3ba4977c9e6ca453b0472571d91287d0f
Tx public key: 3d621867a7d2b7b5e0a7ef22c9bcd5cef52879af2b517cf49bbb8823238606e5
Timestamp: 1736286869 Timestamp [UCT]: 2025-01-07 21:54:29 Age [y:d:h:m:s]: 00:153:00:12:48
Block: 1192444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109187 RingCT/type: yes/0
Extra: 013d621867a7d2b7b5e0a7ef22c9bcd5cef52879af2b517cf49bbb8823238606e50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68f91e49330feb47b376917b5035e16715397b64620685b2ef6c5dc0fcfd6118 0.600000000000 1678997 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": 1192454, "vin": [ { "gen": { "height": 1192444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68f91e49330feb47b376917b5035e16715397b64620685b2ef6c5dc0fcfd6118" } } ], "extra": [ 1, 61, 98, 24, 103, 167, 210, 183, 181, 224, 167, 239, 34, 201, 188, 213, 206, 245, 40, 121, 175, 43, 81, 124, 244, 155, 187, 136, 35, 35, 134, 6, 229, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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