Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b63c9ab6091114ee67b8a07fdfe51b4b3c05e2bfea416712e8c024eeb8c10f0

Tx prefix hash: 0bd5727a17e1c8c7bfb34639fa19e0d639ce8d068d3f9f316224049ed7c3e46b
Tx public key: d8f26bd344adb3bb7346aa74427620c4dcdf02b64e473991e9ad482502e6fe27
Timestamp: 1766014686 Timestamp [UCT]: 2025-12-17 23:38:06 Age [y:d:h:m:s]: 00:004:11:00:48
Block: 1435898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3193 RingCT/type: yes/0
Extra: 01d8f26bd344adb3bb7346aa74427620c4dcdf02b64e473991e9ad482502e6fe270211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b23c756bc315cc834f823e89afd025df49a048276ab7985c4ff8168b15411c5 0.600000000000 1924703 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": 1435908, "vin": [ { "gen": { "height": 1435898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b23c756bc315cc834f823e89afd025df49a048276ab7985c4ff8168b15411c5" } } ], "extra": [ 1, 216, 242, 107, 211, 68, 173, 179, 187, 115, 70, 170, 116, 66, 118, 32, 196, 220, 223, 2, 182, 78, 71, 57, 145, 233, 173, 72, 37, 2, 230, 254, 39, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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