Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae7700c009cb9c3a8ed0f55dbad0d8200c86e98f695ab501476d9aed9db78ec

Tx prefix hash: 64468324fb3ec3759fd00501fab4c729a5979df47a855a801c68013bccbbeb36
Tx public key: 75e1d99ec56a7d3dda5f26dfbe628a4c261576d26571819432aa5c6c272ba041
Timestamp: 1745873941 Timestamp [UCT]: 2025-04-28 20:59:01 Age [y:d:h:m:s]: 00:276:22:45:25
Block: 1271553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195558 RingCT/type: yes/0
Extra: 0175e1d99ec56a7d3dda5f26dfbe628a4c261576d26571819432aa5c6c272ba04102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af10acef745275fdd98d49cd111ef15e6a026e67cb157e66b09bafe5ffaa031 0.600000000000 1758816 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": 1271563, "vin": [ { "gen": { "height": 1271553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af10acef745275fdd98d49cd111ef15e6a026e67cb157e66b09bafe5ffaa031" } } ], "extra": [ 1, 117, 225, 217, 158, 197, 106, 125, 61, 218, 95, 38, 223, 190, 98, 138, 76, 38, 21, 118, 210, 101, 113, 129, 148, 50, 170, 92, 108, 39, 43, 160, 65, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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