Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d823dfd45ef2dd4ec4d84b15cbbc513d2b3a2825adf44cb5fbac123a460e2b

Tx prefix hash: 02ea42d560d4e703688bab196c3fab3a8946954d256fa772cf069eb2dd6896dd
Tx public key: a3214b74fc3ad31d0e84bc69660c6304e758d355b607fa3f5814f70ca8ecfe1c
Timestamp: 1752168394 Timestamp [UCT]: 2025-07-10 17:26:34 Age [y:d:h:m:s]: 00:133:22:07:56
Block: 1322760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94273 RingCT/type: yes/0
Extra: 01a3214b74fc3ad31d0e84bc69660c6304e758d355b607fa3f5814f70ca8ecfe1c02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 037bb3b9d23cbc214e9ab70e55d22eba0da0a28eb6ccffb821e6c940b1d7a192 0.600000000000 1810491 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": 1322770, "vin": [ { "gen": { "height": 1322760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "037bb3b9d23cbc214e9ab70e55d22eba0da0a28eb6ccffb821e6c940b1d7a192" } } ], "extra": [ 1, 163, 33, 75, 116, 252, 58, 211, 29, 14, 132, 188, 105, 102, 12, 99, 4, 231, 88, 211, 85, 182, 7, 250, 63, 88, 20, 247, 12, 168, 236, 254, 28, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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