Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de5c3c21c246fe469a51d7ba7b671d7677d00557a2d10e9266581f008d098534

Tx prefix hash: e0d540616b52e4533b024ba308edcad9fb047ac137af9182e341bc2adea9ad75
Tx public key: 21fc9938d39ed93f26f4c573a9c3c011ab8545d5f5a444eff4c3fa2b6b0d2d0f
Timestamp: 1722783092 Timestamp [UCT]: 2024-08-04 14:51:32 Age [y:d:h:m:s]: 01:096:16:07:07
Block: 1080622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327575 RingCT/type: yes/0
Extra: 0121fc9938d39ed93f26f4c573a9c3c011ab8545d5f5a444eff4c3fa2b6b0d2d0f02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 066a1868cdb64227b6762a57510cefe232f29de11bea371cc4c47c8272b8357a 0.600000000000 1554057 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": 1080632, "vin": [ { "gen": { "height": 1080622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "066a1868cdb64227b6762a57510cefe232f29de11bea371cc4c47c8272b8357a" } } ], "extra": [ 1, 33, 252, 153, 56, 211, 158, 217, 63, 38, 244, 197, 115, 169, 195, 192, 17, 171, 133, 69, 213, 245, 164, 68, 239, 244, 195, 250, 43, 107, 13, 45, 15, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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