Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4153e5e113ab33188bda8948bd9a23d4a935dc26045de7f0bd1c2fae4dd033

Tx prefix hash: 32aa4b8a5ec359b47cc82c8a0d8330766caaebe24d02d6db279cc5184ddcdf7d
Tx public key: b471b8b6c191aa7160691e5866241d30b1352db054c4718dd582cfa3e5724564
Timestamp: 1734288445 Timestamp [UCT]: 2024-12-15 18:47:25 Age [y:d:h:m:s]: 00:103:16:43:26
Block: 1175926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73879 RingCT/type: yes/0
Extra: 01b471b8b6c191aa7160691e5866241d30b1352db054c4718dd582cfa3e5724564021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61f550ab5efaeeb6ee3e2e55c4cc4bcdfda28c5d1a8a9f91843e670d90e54ec4 0.600000000000 1662253 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": 1175936, "vin": [ { "gen": { "height": 1175926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61f550ab5efaeeb6ee3e2e55c4cc4bcdfda28c5d1a8a9f91843e670d90e54ec4" } } ], "extra": [ 1, 180, 113, 184, 182, 193, 145, 170, 113, 96, 105, 30, 88, 102, 36, 29, 48, 177, 53, 45, 176, 84, 196, 113, 141, 213, 130, 207, 163, 229, 114, 69, 100, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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