Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e9c9396b259e22c82bc223122a16f271dc2b3f678fde610f23e513495b1285a

Tx prefix hash: 66180956d7d91e7128dea8f759310af40d0fdd8c1f0b7b9dfecdc8e35397c938
Tx public key: 48596801b30661a12b6d1aff2c284b5d014cccbdba6dbf32ec01b0285f71cda5
Timestamp: 1709263158 Timestamp [UCT]: 2024-03-01 03:19:18 Age [y:d:h:m:s]: 01:039:11:34:57
Block: 968551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289220 RingCT/type: yes/0
Extra: 0148596801b30661a12b6d1aff2c284b5d014cccbdba6dbf32ec01b0285f71cda502110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 265ef7dd540fbeac79e55e1c6d3ff06e4d9c4f753cd6fb2edb8bc6c0f2e244ad 0.600000000000 1428368 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": 968561, "vin": [ { "gen": { "height": 968551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "265ef7dd540fbeac79e55e1c6d3ff06e4d9c4f753cd6fb2edb8bc6c0f2e244ad" } } ], "extra": [ 1, 72, 89, 104, 1, 179, 6, 97, 161, 43, 109, 26, 255, 44, 40, 75, 93, 1, 76, 204, 189, 186, 109, 191, 50, 236, 1, 176, 40, 95, 113, 205, 165, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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