Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80046f8f29124cfaba5afc35a7a32f54bde5dc09f9da756bae0003290ded0059

Tx prefix hash: 361c544c8aa2c464cb0616bd9ee46267aa30d67adba3ca9b77e3a4e09e74770c
Tx public key: 8c834ab7b839dec2400d7b99d45d1071d2a1123c05459b2fb2f5116e093b08ed
Timestamp: 1748970536 Timestamp [UCT]: 2025-06-03 17:08:56 Age [y:d:h:m:s]: 00:166:05:07:25
Block: 1297196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116474 RingCT/type: yes/0
Extra: 018c834ab7b839dec2400d7b99d45d1071d2a1123c05459b2fb2f5116e093b08ed02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875be09351d4f6b58e48f4e883364a370aac79c2b9d0fc5950c68f2307680a68 0.600000000000 1784713 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": 1297206, "vin": [ { "gen": { "height": 1297196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875be09351d4f6b58e48f4e883364a370aac79c2b9d0fc5950c68f2307680a68" } } ], "extra": [ 1, 140, 131, 74, 183, 184, 57, 222, 194, 64, 13, 123, 153, 212, 93, 16, 113, 210, 161, 18, 60, 5, 69, 155, 47, 178, 245, 17, 110, 9, 59, 8, 237, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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