Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc1028df1fb6d293a1b88a8493da5be8ce817341e78c6bf70c6e6001099a9a6

Tx prefix hash: 4b87d9302736f67791fd3837f154d91ed774981e9e13d68c348899db4980c11d
Tx public key: a17eac7c56050d85a9d1cd70a75182cb3ac1f5d5d4dabb57e37c160cebeee180
Timestamp: 1737395183 Timestamp [UCT]: 2025-01-20 17:46:23 Age [y:d:h:m:s]: 00:148:18:04:19
Block: 1201580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106061 RingCT/type: yes/0
Extra: 01a17eac7c56050d85a9d1cd70a75182cb3ac1f5d5d4dabb57e37c160cebeee1800211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa809cebd2b25a2bda599b37088c35d14ac0913feb03a6a5a50b381702a0602 0.600000000000 1688233 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": 1201590, "vin": [ { "gen": { "height": 1201580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa809cebd2b25a2bda599b37088c35d14ac0913feb03a6a5a50b381702a0602" } } ], "extra": [ 1, 161, 126, 172, 124, 86, 5, 13, 133, 169, 209, 205, 112, 167, 81, 130, 203, 58, 193, 245, 213, 212, 218, 187, 87, 227, 124, 22, 12, 235, 238, 225, 128, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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