Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697b6a24765590c7564f154eeafc119546c297b18195c06c7a84f0bcf5cbfb16

Tx prefix hash: b9bce6113263f9211f3e7eb3c36050f58df7bf6fd1ff024f7db4cc920662b075
Tx public key: 1bde5844e8aabe1e7f3098fc1dfc65167a003ec334ea43bfa8d5125f2bc4aa1a
Timestamp: 1762689302 Timestamp [UCT]: 2025-11-09 11:55:02 Age [y:d:h:m:s]: 00:044:16:48:21
Block: 1408348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32002 RingCT/type: yes/0
Extra: 011bde5844e8aabe1e7f3098fc1dfc65167a003ec334ea43bfa8d5125f2bc4aa1a0211000000088368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769f45d55fd71a4bd8c9a47cc425430a30c6f9aa14431a7282a5bc402175cca0 0.600000000000 1896777 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": 1408358, "vin": [ { "gen": { "height": 1408348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769f45d55fd71a4bd8c9a47cc425430a30c6f9aa14431a7282a5bc402175cca0" } } ], "extra": [ 1, 27, 222, 88, 68, 232, 170, 190, 30, 127, 48, 152, 252, 29, 252, 101, 22, 122, 0, 62, 195, 52, 234, 67, 191, 168, 213, 18, 95, 43, 196, 170, 26, 2, 17, 0, 0, 0, 8, 131, 104, 38, 109, 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