Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a353bd21e2c238e805044e2d8aacf01ac0f7328653a5e6f45fa641c8f59c9b7

Tx prefix hash: 6dc8aa1f7190ecdc8df8f5fd51bb691daa8efe04b462b82f5ace865be7c4848b
Tx public key: bc31cb9745b0cef2a98859b0ed78af29f012b49ff03260badc688a767206f540
Timestamp: 1760606607 Timestamp [UCT]: 2025-10-16 09:23:27 Age [y:d:h:m:s]: 00:077:11:29:29
Block: 1391090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55475 RingCT/type: yes/0
Extra: 01bc31cb9745b0cef2a98859b0ed78af29f012b49ff03260badc688a767206f5400211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ee31a638fd41d7fcc7f6adc3d50768ebc524e1dfa07c2e5e980ce145d5e3e39 0.600000000000 1879337 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": 1391100, "vin": [ { "gen": { "height": 1391090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ee31a638fd41d7fcc7f6adc3d50768ebc524e1dfa07c2e5e980ce145d5e3e39" } } ], "extra": [ 1, 188, 49, 203, 151, 69, 176, 206, 242, 169, 136, 89, 176, 237, 120, 175, 41, 240, 18, 180, 159, 240, 50, 96, 186, 220, 104, 138, 118, 114, 6, 245, 64, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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