Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41eafd1440eaeb2493befd6ea4e1fa144f6dbfdcc273b22164ee006b6b898837

Tx prefix hash: a20805356483867c2a2a2c9ed4b3f8eeb3d27f60aff7bac69f2222242c320405
Tx public key: 7fa37d965bdc3332c1cd78e03a2e4a084a38ecfc7c4cf667385317ea415f6bf3
Timestamp: 1707580281 Timestamp [UCT]: 2024-02-10 15:51:21 Age [y:d:h:m:s]: 01:109:12:10:40
Block: 954584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339356 RingCT/type: yes/0
Extra: 017fa37d965bdc3332c1cd78e03a2e4a084a38ecfc7c4cf667385317ea415f6bf3021100000002ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7adc065347bd16625dff04160a6434469ae58be2ab88cd424e6a2ea2c76226 0.600000000000 1413864 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": 954594, "vin": [ { "gen": { "height": 954584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7adc065347bd16625dff04160a6434469ae58be2ab88cd424e6a2ea2c76226" } } ], "extra": [ 1, 127, 163, 125, 150, 91, 220, 51, 50, 193, 205, 120, 224, 58, 46, 74, 8, 74, 56, 236, 252, 124, 76, 246, 103, 56, 83, 23, 234, 65, 95, 107, 243, 2, 17, 0, 0, 0, 2, 236, 87, 178, 52, 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