Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc962d28bad69a79c136bac42b4af983b18069ba95304cc28c8b1715a583d34

Tx prefix hash: 9e92531225831fbd64b729ef867c37f6d3aa75fa3d90dfa6a34dd652cab3a65e
Tx public key: 5eeaaaf9102f2edc3175a6a2c6b5dc337e328f6baecaffa8110101985d41e9d6
Timestamp: 1739773549 Timestamp [UCT]: 2025-02-17 06:25:49 Age [y:d:h:m:s]: 00:276:19:13:48
Block: 1221009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195609 RingCT/type: yes/0
Extra: 015eeaaaf9102f2edc3175a6a2c6b5dc337e328f6baecaffa8110101985d41e9d6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02fe49eb0a3f79858cfed6a1a5f99f3c442d2b6864b62d90720a5b8b4dfface 0.600000000000 1707852 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": 1221019, "vin": [ { "gen": { "height": 1221009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02fe49eb0a3f79858cfed6a1a5f99f3c442d2b6864b62d90720a5b8b4dfface" } } ], "extra": [ 1, 94, 234, 170, 249, 16, 47, 46, 220, 49, 117, 166, 162, 198, 181, 220, 51, 126, 50, 143, 107, 174, 202, 255, 168, 17, 1, 1, 152, 93, 65, 233, 214, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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