Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6569a41f2b0e04b68d1b3757e64ad386942d2fddb28070c175a8fca8300b9004

Tx prefix hash: 5acecd3d0a3509c76c400bb3b58e8e7284bd2c1e48261707870d305e8b5890b9
Tx public key: 2ea1907b97f859ac86dd035417ec5b22adb4c2205f655211739039e87b56dc86
Timestamp: 1738256496 Timestamp [UCT]: 2025-01-30 17:01:36 Age [y:d:h:m:s]: 00:137:00:00:00
Block: 1208485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97895 RingCT/type: yes/0
Extra: 012ea1907b97f859ac86dd035417ec5b22adb4c2205f655211739039e87b56dc860211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff6e38a891fe840a4f0f81693012c9ac81d8a0259d8aea31a8c59a8efc04a20c 0.600000000000 1695218 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": 1208495, "vin": [ { "gen": { "height": 1208485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff6e38a891fe840a4f0f81693012c9ac81d8a0259d8aea31a8c59a8efc04a20c" } } ], "extra": [ 1, 46, 161, 144, 123, 151, 248, 89, 172, 134, 221, 3, 84, 23, 236, 91, 34, 173, 180, 194, 32, 95, 101, 82, 17, 115, 144, 57, 232, 123, 86, 220, 134, 2, 17, 0, 0, 0, 4, 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