Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb85e4460612dbd45fd1ea207d8de34fdfca346bcc5c986baab417f975ef5efc

Tx prefix hash: 9385afe9b8226780dff33bc7dd35a809687d3b32f3328123903bf31500549a34
Tx public key: 6f0e4c64c8e0f8dd845250dcac3f3f4505f87f56fee1f8480dfdb2c9835b18a2
Timestamp: 1734318790 Timestamp [UCT]: 2024-12-16 03:13:10 Age [y:d:h:m:s]: 00:186:06:04:35
Block: 1176167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132782 RingCT/type: yes/0
Extra: 016f0e4c64c8e0f8dd845250dcac3f3f4505f87f56fee1f8480dfdb2c9835b18a2021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e8b04cedc57c40b9d0f2cae1cd77bce62421ba190e1e2081bc15c0010288f4e 0.600000000000 1662498 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": 1176177, "vin": [ { "gen": { "height": 1176167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e8b04cedc57c40b9d0f2cae1cd77bce62421ba190e1e2081bc15c0010288f4e" } } ], "extra": [ 1, 111, 14, 76, 100, 200, 224, 248, 221, 132, 82, 80, 220, 172, 63, 63, 69, 5, 248, 127, 86, 254, 225, 248, 72, 13, 253, 178, 201, 131, 91, 24, 162, 2, 17, 0, 0, 0, 5, 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