Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7fbddc6b6186c46723fc7e105f258927fea3a68faa8a2f0d718180b8023f902

Tx prefix hash: 3adc1c4a06bc40190e16652d40a95bfaeb3997ca08d31e5b6616efa15a723655
Tx public key: 0435ed930e629c99a890312f40603f289fdc90818d24322c0d597d5956c43baf
Timestamp: 1750229441 Timestamp [UCT]: 2025-06-18 06:50:41 Age [y:d:h:m:s]: 00:155:13:33:00
Block: 1307485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108982 RingCT/type: yes/0
Extra: 010435ed930e629c99a890312f40603f289fdc90818d24322c0d597d5956c43baf021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fac166cafaefc4a05d14f941b268fc722173e4894fb47d273d517c1b24ee089 0.600000000000 1795096 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": 1307495, "vin": [ { "gen": { "height": 1307485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fac166cafaefc4a05d14f941b268fc722173e4894fb47d273d517c1b24ee089" } } ], "extra": [ 1, 4, 53, 237, 147, 14, 98, 156, 153, 168, 144, 49, 47, 64, 96, 63, 40, 159, 220, 144, 129, 141, 36, 50, 44, 13, 89, 125, 89, 86, 196, 59, 175, 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