Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff9090f3c76b387a5b81e4a92766b79790d2a64844771d65105cc5408959fac9

Tx prefix hash: f90f86e1185005a7a21b819c60d6bbaaf48692237f0d3b90b1eec4069b91c3ed
Tx public key: 28660c2d516aa76b835464c8893eeb385d14e4a2d11b7e4b337dd6e493ee1e14
Timestamp: 1725627185 Timestamp [UCT]: 2024-09-06 12:53:05 Age [y:d:h:m:s]: 00:169:03:03:43
Block: 1104216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120660 RingCT/type: yes/0
Extra: 0128660c2d516aa76b835464c8893eeb385d14e4a2d11b7e4b337dd6e493ee1e1402110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2115b9af87d81419541c5ec587a8a82f522a69ad3f7df37a2b92631d8cae80c 0.600000000000 1581295 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": 1104226, "vin": [ { "gen": { "height": 1104216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2115b9af87d81419541c5ec587a8a82f522a69ad3f7df37a2b92631d8cae80c" } } ], "extra": [ 1, 40, 102, 12, 45, 81, 106, 167, 107, 131, 84, 100, 200, 137, 62, 235, 56, 93, 20, 228, 162, 209, 27, 126, 75, 51, 125, 214, 228, 147, 238, 30, 20, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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