Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3e0f0206c7884f73b05aa00327a01d3dd6f0078ad1d5dabd55271d537b24da

Tx prefix hash: f7feaadb46168365808132179bf7ee8d4a14d7579e2dd6ed21cb4987ecaa7588
Tx public key: 471798c3a71f71e1f15a528e632cd4baae4e83c61ae842d0d6097be93aec9f4e
Timestamp: 1714164296 Timestamp [UCT]: 2024-04-26 20:44:56 Age [y:d:h:m:s]: 01:021:08:58:06
Block: 1009166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276238 RingCT/type: yes/0
Extra: 01471798c3a71f71e1f15a528e632cd4baae4e83c61ae842d0d6097be93aec9f4e02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 051cefb7e04762dc87657314ab28b4007a4ddfbd8b142405f832f212c37f9257 0.600000000000 1470760 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": 1009176, "vin": [ { "gen": { "height": 1009166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "051cefb7e04762dc87657314ab28b4007a4ddfbd8b142405f832f212c37f9257" } } ], "extra": [ 1, 71, 23, 152, 195, 167, 31, 113, 225, 241, 90, 82, 142, 99, 44, 212, 186, 174, 78, 131, 198, 26, 232, 66, 208, 214, 9, 123, 233, 58, 236, 159, 78, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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