Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed316b520868a27c15fa7620d0a8de7cf395a4dadc3970edb844482da7b831ab

Tx prefix hash: bab25ca428c3efe899a22f64279053c53d397bb29f1331f79a54d5611e118d1b
Tx public key: f353cf98f9032617aa9b7fe21f1f6e4d1815e4b66a457c6eebc9cc162d6e87f8
Timestamp: 1732698749 Timestamp [UCT]: 2024-11-27 09:12:29 Age [y:d:h:m:s]: 00:042:17:02:43
Block: 1162742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30546 RingCT/type: yes/0
Extra: 01f353cf98f9032617aa9b7fe21f1f6e4d1815e4b66a457c6eebc9cc162d6e87f8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35644ff1f2849cf2abee57b2435ef6693320de6ee02d05f3bbcc37d6c4d2b73d 0.600000000000 1648399 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": 1162752, "vin": [ { "gen": { "height": 1162742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35644ff1f2849cf2abee57b2435ef6693320de6ee02d05f3bbcc37d6c4d2b73d" } } ], "extra": [ 1, 243, 83, 207, 152, 249, 3, 38, 23, 170, 155, 127, 226, 31, 31, 110, 77, 24, 21, 228, 182, 106, 69, 124, 110, 235, 201, 204, 22, 45, 110, 135, 248, 2, 17, 0, 0, 0, 5, 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