Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f73328db78a85f22a2d9c255b34db9a5cf9bcea5462135a41df7ca77096c91c

Tx prefix hash: e641e7aaf596f902562663784a586f38f385057c3f23cf19bc207dae24076708
Tx public key: bfcec50f90f41c8acb521812a3d186842ae5e0c8a73557b64ef26a16673f4ea4
Timestamp: 1739100724 Timestamp [UCT]: 2025-02-09 11:32:04 Age [y:d:h:m:s]: 00:353:07:31:58
Block: 1215470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250191 RingCT/type: yes/0
Extra: 01bfcec50f90f41c8acb521812a3d186842ae5e0c8a73557b64ef26a16673f4ea40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8214356c50f5b2662c1562d074e69b00de8a3fb6ea200a0288be621255e0f05 0.600000000000 1702269 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": 1215480, "vin": [ { "gen": { "height": 1215470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8214356c50f5b2662c1562d074e69b00de8a3fb6ea200a0288be621255e0f05" } } ], "extra": [ 1, 191, 206, 197, 15, 144, 244, 28, 138, 203, 82, 24, 18, 163, 209, 134, 132, 42, 229, 224, 200, 167, 53, 87, 182, 78, 242, 106, 22, 103, 63, 78, 164, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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