Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5053d083a2958e873b491a8a1b6e4a992bf453dc10913ccd52351f420f9e300

Tx prefix hash: bf24c175cd591e10f895851fa907f604c7fb968130b13d3ad16877e1a2ebc0ba
Tx public key: aa45c90b7911cd0f4ce854eeb43f39d718eb0fa1d1f057d740470540c72885ed
Timestamp: 1750456302 Timestamp [UCT]: 2025-06-20 21:51:42 Age [y:d:h:m:s]: 00:146:06:54:16
Block: 1309312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102400 RingCT/type: yes/0
Extra: 01aa45c90b7911cd0f4ce854eeb43f39d718eb0fa1d1f057d740470540c72885ed021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e89c5a2ecc3f2bf75e178606f074eb928e13df0b215ddf6df5b0c556eec45008 0.600000000000 1796927 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": 1309322, "vin": [ { "gen": { "height": 1309312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e89c5a2ecc3f2bf75e178606f074eb928e13df0b215ddf6df5b0c556eec45008" } } ], "extra": [ 1, 170, 69, 201, 11, 121, 17, 205, 15, 76, 232, 84, 238, 180, 63, 57, 215, 24, 235, 15, 161, 209, 240, 87, 215, 64, 71, 5, 64, 199, 40, 133, 237, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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