Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8ece2439387976e1eddd9e1d95fb4c8fddf4f36e46168ed3f93ea9aff70b0f

Tx prefix hash: 61daa268656c35a12d16359ff800912cbb32850b77d77ae9b4f8d5ea5cefc5ef
Tx public key: c913a06c4e6d0878de227e4a28522a6b8bc3c852d9838ef66506665cf3a9dd15
Timestamp: 1717441948 Timestamp [UCT]: 2024-06-03 19:12:28 Age [y:d:h:m:s]: 00:298:14:53:06
Block: 1036359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213403 RingCT/type: yes/0
Extra: 01c913a06c4e6d0878de227e4a28522a6b8bc3c852d9838ef66506665cf3a9dd150211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd8b67970aba21d1e97f4519b1fe07bb810aeda457f09891041cd6966f3536f6 0.600000000000 1504886 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": 1036369, "vin": [ { "gen": { "height": 1036359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd8b67970aba21d1e97f4519b1fe07bb810aeda457f09891041cd6966f3536f6" } } ], "extra": [ 1, 201, 19, 160, 108, 78, 109, 8, 120, 222, 34, 126, 74, 40, 82, 42, 107, 139, 195, 200, 82, 217, 131, 142, 246, 101, 6, 102, 92, 243, 169, 221, 21, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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