Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de412d33fcfe8c29c796b3a2d4f7221355ab1008658ed5b80f8129a49748eb96

Tx prefix hash: 1f32de40a5581e087a7ab208a7c2823c1f39ce11e944496b3d6ee4f7d0dda29e
Tx public key: 6cf73afedea09946b25fc8c7a1711c1a3fc2f7b7501eadca23802cb68ecf3222
Timestamp: 1739138323 Timestamp [UCT]: 2025-02-09 21:58:43 Age [y:d:h:m:s]: 00:356:12:07:08
Block: 1215785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252470 RingCT/type: yes/0
Extra: 016cf73afedea09946b25fc8c7a1711c1a3fc2f7b7501eadca23802cb68ecf3222021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff45eebc94ee7ff9b8ea522fda7509e29b423ebe101023468812dab4f258e51 0.600000000000 1702584 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": 1215795, "vin": [ { "gen": { "height": 1215785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff45eebc94ee7ff9b8ea522fda7509e29b423ebe101023468812dab4f258e51" } } ], "extra": [ 1, 108, 247, 58, 254, 222, 160, 153, 70, 178, 95, 200, 199, 161, 113, 28, 26, 63, 194, 247, 183, 80, 30, 173, 202, 35, 128, 44, 182, 142, 207, 50, 34, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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