Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29de9aa4dcc77fd1f61dccc68a5cbea27bdab0404749af12cf29a64ea7040fae

Tx prefix hash: f3168724226a828744853d9831bc939de0f1eaa674331ac4f6e8eeb5c831d23a
Tx public key: dd29b380f4553ee9a849de55278905fc3369f533740c0e147d4751d4f5a9e221
Timestamp: 1727142425 Timestamp [UCT]: 2024-09-24 01:47:05 Age [y:d:h:m:s]: 00:061:16:46:09
Block: 1116765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44101 RingCT/type: yes/0
Extra: 01dd29b380f4553ee9a849de55278905fc3369f533740c0e147d4751d4f5a9e22102110000000691e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: c7123e3baa798bafbc14aba8eaa74453316cc2d9fe630ca231a3d058b4b17284 0.608000000000 1597362 of 0

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": 1116775, "vin": [ { "gen": { "height": 1116765 } } ], "vout": [ { "amount": 608000000, "target": { "key": "c7123e3baa798bafbc14aba8eaa74453316cc2d9fe630ca231a3d058b4b17284" } } ], "extra": [ 1, 221, 41, 179, 128, 244, 85, 62, 233, 168, 73, 222, 85, 39, 137, 5, 252, 51, 105, 245, 51, 116, 12, 14, 20, 125, 71, 81, 212, 245, 169, 226, 33, 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