Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4953a2ad8a5f6851acd4e9e5eb3de4fd21702d615d98dfdbf0c19448b18026e8

Tx prefix hash: 12a14ee473f7580de191a57b25c8ff4adb1dcb0c60284e3dd3e407edbbe8f90e
Tx public key: 905096e8cdeed8d58893d5769c0be5126ccd2305c864fe9262f0788bd47b19ed
Timestamp: 1676705338 Timestamp [UCT]: 2023-02-18 07:28:58 Age [y:d:h:m:s]: 02:071:00:45:52
Block: 699500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572394 RingCT/type: yes/0
Extra: 01905096e8cdeed8d58893d5769c0be5126ccd2305c864fe9262f0788bd47b19ed02110000000433af99f4000000000000000000

1 output(s) for total of 2.953017616000 dcy

stealth address amount amount idx
00: dca63656cd6cd4f05e5c40236b89eb380d6936f3bf947e80bdb931187474eee7 2.953017616000 1142913 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": 699510, "vin": [ { "gen": { "height": 699500 } } ], "vout": [ { "amount": 2953017616, "target": { "key": "dca63656cd6cd4f05e5c40236b89eb380d6936f3bf947e80bdb931187474eee7" } } ], "extra": [ 1, 144, 80, 150, 232, 205, 238, 216, 213, 136, 147, 213, 118, 156, 11, 229, 18, 108, 205, 35, 5, 200, 100, 254, 146, 98, 240, 120, 139, 212, 123, 25, 237, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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