Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 461f1ed7eb96615cf3cdf43660b99f6c7797d3fe40fcf859b0ee036286a17c84

Tx prefix hash: a27b5b9b171aa4e06af72cdeb28028e224d4c7df401f385c849e0bf59214e77b
Tx public key: f8d7ba6dcbd4dc1d7ffd8d96c4ae1079179e66e8a0cf2fc92f624cb53d31d8d1
Timestamp: 1720372197 Timestamp [UCT]: 2024-07-07 17:09:57 Age [y:d:h:m:s]: 01:122:14:33:22
Block: 1060641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346149 RingCT/type: yes/0
Extra: 01f8d7ba6dcbd4dc1d7ffd8d96c4ae1079179e66e8a0cf2fc92f624cb53d31d8d102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c2a25445396ccda4fe1da90614e189adf5db34bb00626450f8e916ea5dfa0ef 0.600000000000 1531126 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": 1060651, "vin": [ { "gen": { "height": 1060641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c2a25445396ccda4fe1da90614e189adf5db34bb00626450f8e916ea5dfa0ef" } } ], "extra": [ 1, 248, 215, 186, 109, 203, 212, 220, 29, 127, 253, 141, 150, 196, 174, 16, 121, 23, 158, 102, 232, 160, 207, 47, 201, 47, 98, 76, 181, 61, 49, 216, 209, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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