Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d27a333133bec492ece889c91c9fc3003a17b886ca18ead7ad717331a3bf7cc

Tx prefix hash: 13346190a98e0138367997bc581548d4fed0e5a5f747c55ac23627d740692c2d
Tx public key: b6eebd30b21ee2b5f6c477a979884cfd6346663d7f2f1df979c04d0b0a08edca
Timestamp: 1766030804 Timestamp [UCT]: 2025-12-18 04:06:44 Age [y:d:h:m:s]: 00:005:10:41:11
Block: 1436038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3886 RingCT/type: yes/0
Extra: 01b6eebd30b21ee2b5f6c477a979884cfd6346663d7f2f1df979c04d0b0a08edca0211000000067b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f64db8a604e8dbfd5acf1d8a1a1f8f7e94e28aa0b62618a3943e2b521b3d892 0.600000000000 1924843 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": 1436048, "vin": [ { "gen": { "height": 1436038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f64db8a604e8dbfd5acf1d8a1a1f8f7e94e28aa0b62618a3943e2b521b3d892" } } ], "extra": [ 1, 182, 238, 189, 48, 178, 30, 226, 181, 246, 196, 119, 169, 121, 136, 76, 253, 99, 70, 102, 61, 127, 47, 29, 249, 121, 192, 77, 11, 10, 8, 237, 202, 2, 17, 0, 0, 0, 6, 123, 30, 81, 172, 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