Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcd90d484151d0296e883e9e1e78022f8446af1471a655ef5ee59461e778c6b5

Tx prefix hash: 4adcc61c0543985cf839e923decce43c02b7627e8a8db9ee284981df96330fb1
Tx public key: e26e5926e0cbbf72ccad331c1599a89552b70abe0c47419c67c3e5102876bd56
Timestamp: 1755352382 Timestamp [UCT]: 2025-08-16 13:53:02 Age [y:d:h:m:s]: 00:142:08:23:03
Block: 1347865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101623 RingCT/type: yes/0
Extra: 01e26e5926e0cbbf72ccad331c1599a89552b70abe0c47419c67c3e5102876bd56021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e11df9135bf1aec3f5dc8aef40f6a2f36382d4e6a9311b6249bf2bcff1adff 0.600000000000 1835786 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": 1347875, "vin": [ { "gen": { "height": 1347865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e11df9135bf1aec3f5dc8aef40f6a2f36382d4e6a9311b6249bf2bcff1adff" } } ], "extra": [ 1, 226, 110, 89, 38, 224, 203, 191, 114, 204, 173, 51, 28, 21, 153, 168, 149, 82, 183, 10, 190, 12, 71, 65, 156, 103, 195, 229, 16, 40, 118, 189, 86, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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