Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c86e5df46480028c1c09185fa2be92135f76c0493523bce517e44e80338a8a

Tx prefix hash: ae1312acf5c64d141f09f6c7c4a40c28441a0918d414cc7d8efb2ddc818e4a70
Tx public key: 2b2430c0dfe538d69e53320ad7a92778dea24a5b15562fc54a9377f175503c06
Timestamp: 1707991611 Timestamp [UCT]: 2024-02-15 10:06:51 Age [y:d:h:m:s]: 01:266:14:54:04
Block: 957997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449315 RingCT/type: yes/0
Extra: 012b2430c0dfe538d69e53320ad7a92778dea24a5b15562fc54a9377f175503c0602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e4cbca0b3016a514b464acd64e1f1bafef638eaf2ff0d732c758b86231c9159 0.600000000000 1417348 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": 958007, "vin": [ { "gen": { "height": 957997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e4cbca0b3016a514b464acd64e1f1bafef638eaf2ff0d732c758b86231c9159" } } ], "extra": [ 1, 43, 36, 48, 192, 223, 229, 56, 214, 158, 83, 50, 10, 215, 169, 39, 120, 222, 162, 74, 91, 21, 86, 47, 197, 74, 147, 119, 241, 117, 80, 60, 6, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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