Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5673ef16e48ff2a172a599c1664bafd8ae163174e60eeef3200d1d03b034c940

Tx prefix hash: badf3bd077482ea5b0201cc803f6332f767dc6f380e1d15d7a3f10ee143b538c
Tx public key: 84c9e0a5d171faaaeea71706d52717ae94e6b7a4eacaa9d63cd0304821e0ce59
Timestamp: 1711585679 Timestamp [UCT]: 2024-03-28 00:27:59 Age [y:d:h:m:s]: 00:308:18:02:09
Block: 987811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220724 RingCT/type: yes/0
Extra: 0184c9e0a5d171faaaeea71706d52717ae94e6b7a4eacaa9d63cd0304821e0ce5902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3686548331a13d44f9b0151eca9b19858003c07975772f5a39e4e8c3874989ef 0.600000000000 1448070 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": 987821, "vin": [ { "gen": { "height": 987811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3686548331a13d44f9b0151eca9b19858003c07975772f5a39e4e8c3874989ef" } } ], "extra": [ 1, 132, 201, 224, 165, 209, 113, 250, 170, 238, 167, 23, 6, 213, 39, 23, 174, 148, 230, 183, 164, 234, 202, 169, 214, 60, 208, 48, 72, 33, 224, 206, 89, 2, 17, 0, 0, 0, 1, 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