Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9488c48c9ddec65dda4825ca76c1b0502ba0db175a7a9830b45c04ca9ae6c6

Tx prefix hash: b07dd8f46c7046c9600d77a1daa4021a7a1d71a934c856aa2cb0ec58fbcd7ba6
Tx public key: e046029a8ca1c1bf66b838683e74ba5aea2d75468991b1816a62549616a0e122
Timestamp: 1754334609 Timestamp [UCT]: 2025-08-04 19:10:09 Age [y:d:h:m:s]: 00:141:07:50:32
Block: 1340281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100010 RingCT/type: yes/0
Extra: 01e046029a8ca1c1bf66b838683e74ba5aea2d75468991b1816a62549616a0e122021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc396032e2d4a77b10212a6da38b41c78e7d37b51029facbc4af5c9c3fa95d77 0.600000000000 1828098 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": 1340291, "vin": [ { "gen": { "height": 1340281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc396032e2d4a77b10212a6da38b41c78e7d37b51029facbc4af5c9c3fa95d77" } } ], "extra": [ 1, 224, 70, 2, 154, 140, 161, 193, 191, 102, 184, 56, 104, 62, 116, 186, 90, 234, 45, 117, 70, 137, 145, 177, 129, 106, 98, 84, 150, 22, 160, 225, 34, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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