Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624a8eafcf61a6877264c4d52cf6a03764a784402532988fd988ed75a813c955

Tx prefix hash: f75c790beb7d12691153629153670c91568a996b8252c7bd58a1055fcae5aa07
Tx public key: 62975d2a25adec25d593bd5a0b7e894f2a4a10c1014e92bc33bfa84ed2e6dba5
Timestamp: 1705550844 Timestamp [UCT]: 2024-01-18 04:07:24 Age [y:d:h:m:s]: 01:006:05:37:14
Block: 937735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265743 RingCT/type: yes/0
Extra: 0162975d2a25adec25d593bd5a0b7e894f2a4a10c1014e92bc33bfa84ed2e6dba502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3478bd9a67408ad479d143feab5d26833f671739656d5ca050b26f3c3e7cb4e7 0.600000000000 1395797 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": 937745, "vin": [ { "gen": { "height": 937735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3478bd9a67408ad479d143feab5d26833f671739656d5ca050b26f3c3e7cb4e7" } } ], "extra": [ 1, 98, 151, 93, 42, 37, 173, 236, 37, 213, 147, 189, 90, 11, 126, 137, 79, 42, 74, 16, 193, 1, 78, 146, 188, 51, 191, 168, 78, 210, 230, 219, 165, 2, 17, 0, 0, 0, 7, 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