Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e57890599e8a44d682170d9da0483adc784296d02ef8db7a943107a08308d5

Tx prefix hash: 471a2519b5a05923f7ea23d2692f475160a971feeb7280ddf2719c7d840fc501
Tx public key: b64b1f4c47c56a674eff3a264c0341c6357853f82e3635f3f7b928c4bb3f073a
Timestamp: 1711168709 Timestamp [UCT]: 2024-03-23 04:38:29 Age [y:d:h:m:s]: 01:230:07:59:22
Block: 984362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423281 RingCT/type: yes/0
Extra: 01b64b1f4c47c56a674eff3a264c0341c6357853f82e3635f3f7b928c4bb3f073a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52bf7197b5b96456d3e36801daff68e9bff3330bae1401fe45cee096705a9377 0.600000000000 1444533 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": 984372, "vin": [ { "gen": { "height": 984362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52bf7197b5b96456d3e36801daff68e9bff3330bae1401fe45cee096705a9377" } } ], "extra": [ 1, 182, 75, 31, 76, 71, 197, 106, 103, 78, 255, 58, 38, 76, 3, 65, 198, 53, 120, 83, 248, 46, 54, 53, 243, 247, 185, 40, 196, 187, 63, 7, 58, 2, 17, 0, 0, 0, 1, 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