Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12fbb7d0a509b9f84cc6fa7eb98efbe6ecff7fa9d1ed29c390683184c66edb58

Tx prefix hash: 5b859c2c3800d5d4247123d7046be922dd4160b70b9be6ddaa5db18565c84883
Tx public key: c57e9ad9cb01833d43d2f6352809d5c3b30a0a41baf2a5b3cd5967e3e80e47c5
Timestamp: 1697288871 Timestamp [UCT]: 2023-10-14 13:07:51 Age [y:d:h:m:s]: 01:178:11:42:28
Block: 869475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388587 RingCT/type: yes/0
Extra: 01c57e9ad9cb01833d43d2f6352809d5c3b30a0a41baf2a5b3cd5967e3e80e47c502110000000333af99f4000000000000000000

1 output(s) for total of 0.807362209000 dcy

stealth address amount amount idx
00: a35d9032ca6ebfcc5957e2e0b3979eec86e8a94f75a5f18cccfe66bcec9f9494 0.807362209000 1324322 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": 869485, "vin": [ { "gen": { "height": 869475 } } ], "vout": [ { "amount": 807362209, "target": { "key": "a35d9032ca6ebfcc5957e2e0b3979eec86e8a94f75a5f18cccfe66bcec9f9494" } } ], "extra": [ 1, 197, 126, 154, 217, 203, 1, 131, 61, 67, 210, 246, 53, 40, 9, 213, 195, 179, 10, 10, 65, 186, 242, 165, 179, 205, 89, 103, 227, 232, 14, 71, 197, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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