Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b92d2f64ff6b9beca1fb737b0e515235f2738662818a2d194e2d6b6ad68cf10c

Tx prefix hash: 6ca5d294402d421b325455657c13bd78ac613f822fbee0180b61097491ed69b6
Tx public key: ce33ccf18355a4a321b7cbec0a2a0a33a5cce6b9a59431cc17142821db66ee5c
Timestamp: 1755469610 Timestamp [UCT]: 2025-08-17 22:26:50 Age [y:d:h:m:s]: 00:141:00:17:32
Block: 1348789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100716 RingCT/type: yes/0
Extra: 01ce33ccf18355a4a321b7cbec0a2a0a33a5cce6b9a59431cc17142821db66ee5c02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4900d1f99f7db20c13204f5f2c7fe4b1eeb4147a730f0992f6ffeb17e458f9ea 0.600000000000 1836718 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": 1348799, "vin": [ { "gen": { "height": 1348789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4900d1f99f7db20c13204f5f2c7fe4b1eeb4147a730f0992f6ffeb17e458f9ea" } } ], "extra": [ 1, 206, 51, 204, 241, 131, 85, 164, 163, 33, 183, 203, 236, 10, 42, 10, 51, 165, 204, 230, 185, 165, 148, 49, 204, 23, 20, 40, 33, 219, 102, 238, 92, 2, 17, 0, 0, 0, 3, 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