Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffad6d3be9bb5112c6b5c4f59ed0a066f40c79ce4492adfdb19c429217f65b77

Tx prefix hash: f5851fb8fd3c4a20b35822834384329a9e137d22ca145733b429e13386acfff0
Tx public key: 26402fc3615cc21894e1f0f0d1bd79548013c738e0f5dc701b01433b749a8c43
Timestamp: 1762613134 Timestamp [UCT]: 2025-11-08 14:45:34 Age [y:d:h:m:s]: 00:019:16:13:21
Block: 1407715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14088 RingCT/type: yes/0
Extra: 0126402fc3615cc21894e1f0f0d1bd79548013c738e0f5dc701b01433b749a8c43021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d701c44ce8fd4775f0fb17ea67c9492ef28a5a8f1fd1b933685ecc58cca354 0.600000000000 1896136 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": 1407725, "vin": [ { "gen": { "height": 1407715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d701c44ce8fd4775f0fb17ea67c9492ef28a5a8f1fd1b933685ecc58cca354" } } ], "extra": [ 1, 38, 64, 47, 195, 97, 92, 194, 24, 148, 225, 240, 240, 209, 189, 121, 84, 128, 19, 199, 56, 224, 245, 220, 112, 27, 1, 67, 59, 116, 154, 140, 67, 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