Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f079bfafa1fcde7115c993adf1f4f6b57741edbef1f274c6e3234a7acd17a2

Tx prefix hash: 49d5bc49201e5470f68b5bb738c3aa8be0765a83703d0363fd6169a5d52b9d11
Tx public key: 6495a0ba430481a4feb003ed9d076c220c07a9434a60bc34f3a4ef4788398452
Timestamp: 1674412147 Timestamp [UCT]: 2023-01-22 18:29:07 Age [y:d:h:m:s]: 02:288:07:48:03
Block: 680489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725405 RingCT/type: yes/0
Extra: 016495a0ba430481a4feb003ed9d076c220c07a9434a60bc34f3a4ef478839845202110000000183600029000000000000000000

1 output(s) for total of 3.413951920000 dcy

stealth address amount amount idx
00: a5d45047428f5fc68da3c317e3c64fd8f1a1b28dbd79000a25c4850dcb0f2147 3.413951920000 1122538 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": 680499, "vin": [ { "gen": { "height": 680489 } } ], "vout": [ { "amount": 3413951920, "target": { "key": "a5d45047428f5fc68da3c317e3c64fd8f1a1b28dbd79000a25c4850dcb0f2147" } } ], "extra": [ 1, 100, 149, 160, 186, 67, 4, 129, 164, 254, 176, 3, 237, 157, 7, 108, 34, 12, 7, 169, 67, 74, 96, 188, 52, 243, 164, 239, 71, 136, 57, 132, 82, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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