Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebd073d126c4a9ee6d8e20b7706880e6c80dcfa68a67036308a490bea8012370

Tx prefix hash: cf4fbdd16acf91f7f47a27b4ad50feab6614b388036108a40e2458f9c216d74a
Tx public key: 61f1bdddd9e4f4a1d0a1a6edbf6528d8febf4b556fd1d6deea80b4c50b8b7978
Timestamp: 1704763625 Timestamp [UCT]: 2024-01-09 01:27:05 Age [y:d:h:m:s]: 01:048:15:26:29
Block: 931220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295847 RingCT/type: yes/0
Extra: 0161f1bdddd9e4f4a1d0a1a6edbf6528d8febf4b556fd1d6deea80b4c50b8b797802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 721f5fd8923ce4f316a2d61043d27f5ae1c79cd617a431976c746994a3522e0d 0.600000000000 1389116 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": 931230, "vin": [ { "gen": { "height": 931220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "721f5fd8923ce4f316a2d61043d27f5ae1c79cd617a431976c746994a3522e0d" } } ], "extra": [ 1, 97, 241, 189, 221, 217, 228, 244, 161, 208, 161, 166, 237, 191, 101, 40, 216, 254, 191, 75, 85, 111, 209, 214, 222, 234, 128, 180, 197, 11, 139, 121, 120, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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