Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b2214ec44e7afd9d6ea22e2ed2b642841441f72dd70e01dad01752a83cd4d5

Tx prefix hash: a71d3d0ea80ea02eec77fc65af86fe15e596c6785630bfcf5f21a565c25d6a93
Tx public key: 0eb2cfec13223b26e3358c8df106a3b9a110e6a160e87672726181d229ee359d
Timestamp: 1700427749 Timestamp [UCT]: 2023-11-19 21:02:29 Age [y:d:h:m:s]: 01:143:18:08:50
Block: 895288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363929 RingCT/type: yes/0
Extra: 010eb2cfec13223b26e3358c8df106a3b9a110e6a160e87672726181d229ee359d021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.663039183000 dcy

stealth address amount amount idx
00: 7192b4b9236d87653e8470559d1388b717329b97ae878a4e8824408c8aa708c2 0.663039183000 1351517 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": 895298, "vin": [ { "gen": { "height": 895288 } } ], "vout": [ { "amount": 663039183, "target": { "key": "7192b4b9236d87653e8470559d1388b717329b97ae878a4e8824408c8aa708c2" } } ], "extra": [ 1, 14, 178, 207, 236, 19, 34, 59, 38, 227, 53, 140, 141, 241, 6, 163, 185, 161, 16, 230, 161, 96, 232, 118, 114, 114, 97, 129, 210, 41, 238, 53, 157, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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