Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5a5ca9550338d429dd3b41d08a85e56ce6d42934f1ef94d6b0d4b2af9334d5

Tx prefix hash: a0b4315ebafb40360bdb689caf73b27d5f1631fac4b7e9ac5dc85cc988acdbf7
Tx public key: d082da2376d1e1815718d49280442bbda64b87d5e3e1b11c4e8599c5ab2e85a5
Timestamp: 1702768678 Timestamp [UCT]: 2023-12-16 23:17:58 Age [y:d:h:m:s]: 01:184:02:19:34
Block: 914694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392640 RingCT/type: yes/0
Extra: 01d082da2376d1e1815718d49280442bbda64b87d5e3e1b11c4e8599c5ab2e85a502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd8a36fa70f8db0f0ff6bf221e1057fb3b172da6bd497f1ff8e0a21b85e16a2a 0.600000000000 1372044 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": 914704, "vin": [ { "gen": { "height": 914694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd8a36fa70f8db0f0ff6bf221e1057fb3b172da6bd497f1ff8e0a21b85e16a2a" } } ], "extra": [ 1, 208, 130, 218, 35, 118, 209, 225, 129, 87, 24, 212, 146, 128, 68, 43, 189, 166, 75, 135, 213, 227, 225, 177, 28, 78, 133, 153, 197, 171, 46, 133, 165, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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