Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e91e24f6ad7841e31323f4ec56fd8e38532a64c6f62ef71f0ad6896d2675ab

Tx prefix hash: c7cb5836f588b3b8b6708f146a3b416335fb65b4ecd01cd4be0a42275fc9747c
Tx public key: 5a7b11c65d3862cacfa48b824ddcaaad046ab7c02a88d7325aa5950a554dd455
Timestamp: 1703119213 Timestamp [UCT]: 2023-12-21 00:40:13 Age [y:d:h:m:s]: 01:176:17:59:03
Block: 917625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387393 RingCT/type: yes/0
Extra: 015a7b11c65d3862cacfa48b824ddcaaad046ab7c02a88d7325aa5950a554dd455021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45b86e68cf2ea6a0036a5b62c09578f16e6504c362383a42bc5109d462c11a42 0.600000000000 1375207 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": 917635, "vin": [ { "gen": { "height": 917625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45b86e68cf2ea6a0036a5b62c09578f16e6504c362383a42bc5109d462c11a42" } } ], "extra": [ 1, 90, 123, 17, 198, 93, 56, 98, 202, 207, 164, 139, 130, 77, 220, 170, 173, 4, 106, 183, 192, 42, 136, 215, 50, 90, 165, 149, 10, 85, 77, 212, 85, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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