Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99516bca99b272b41200f7ef47c3f14ac20385b28859568e494d965fe8aa9f4f

Tx prefix hash: 31aeb9f1aaa7a93d5fded58194fac339678923a94f1ad08b20261132f645dfd8
Tx public key: 3bb65e5d53ba4e950a3240c79e38a4fa83f25a6068a13f01c83b04aef0f19624
Timestamp: 1694773089 Timestamp [UCT]: 2023-09-15 10:18:09 Age [y:d:h:m:s]: 01:162:20:14:03
Block: 848595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377438 RingCT/type: yes/0
Extra: 013bb65e5d53ba4e950a3240c79e38a4fa83f25a6068a13f01c83b04aef0f19624021100000007faf35c9c000000000000000000

1 output(s) for total of 0.946787586000 dcy

stealth address amount amount idx
00: d2ce036ee96721b2bdfe44b403eb8d2fde78aa15dbbf6fd4bf9676005f505ce7 0.946787586000 1302209 of 0

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": 848605, "vin": [ { "gen": { "height": 848595 } } ], "vout": [ { "amount": 946787586, "target": { "key": "d2ce036ee96721b2bdfe44b403eb8d2fde78aa15dbbf6fd4bf9676005f505ce7" } } ], "extra": [ 1, 59, 182, 94, 93, 83, 186, 78, 149, 10, 50, 64, 199, 158, 56, 164, 250, 131, 242, 90, 96, 104, 161, 63, 1, 200, 59, 4, 174, 240, 241, 150, 36, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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