Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e0ed30f65bac30bfc893f1c1b1c46d5aeed87f344ccdd78bf18144a44264e76

Tx prefix hash: bd46080c97c93de89d0e1ed87302f5d402ed2935636ee75ff1aec9206dc2d8a8
Tx public key: 28c1037c9cd48ed2373d3168a3a8f29a11fd5201d3a858b0b41eb015ef25151d
Timestamp: 1746393749 Timestamp [UCT]: 2025-05-04 21:22:29 Age [y:d:h:m:s]: 00:200:01:07:06
Block: 1275844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140688 RingCT/type: yes/0
Extra: 0128c1037c9cd48ed2373d3168a3a8f29a11fd5201d3a858b0b41eb015ef25151d0211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad40c79f5f1759e80e8f1abd23d4cb3bdfe685e0343b7c041d40697c0472ef4e 0.600000000000 1763159 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": 1275854, "vin": [ { "gen": { "height": 1275844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad40c79f5f1759e80e8f1abd23d4cb3bdfe685e0343b7c041d40697c0472ef4e" } } ], "extra": [ 1, 40, 193, 3, 124, 156, 212, 142, 210, 55, 61, 49, 104, 163, 168, 242, 154, 17, 253, 82, 1, 211, 168, 88, 176, 180, 30, 176, 21, 239, 37, 21, 29, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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