Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238c1d2b21abc0550715a1c55f54c4578c85f6a95dccb7f858ea205915e246b1

Tx prefix hash: 0d36538de575dbbaaf7896e2ee3d0f46b7ca82649b43b438ce238eaec3843a8d
Tx public key: f7107c693cb00c742756f5ef3f1370220b019dfd577b56686afe94647a832986
Timestamp: 1710731958 Timestamp [UCT]: 2024-03-18 03:19:18 Age [y:d:h:m:s]: 01:093:02:06:34
Block: 980740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327394 RingCT/type: yes/0
Extra: 01f7107c693cb00c742756f5ef3f1370220b019dfd577b56686afe94647a83298602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d53ea20edaec0b838a42b53629c13bbac061b9c9e8e55de410e658d4e6f51b5d 0.600000000000 1440821 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": 980750, "vin": [ { "gen": { "height": 980740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53ea20edaec0b838a42b53629c13bbac061b9c9e8e55de410e658d4e6f51b5d" } } ], "extra": [ 1, 247, 16, 124, 105, 60, 176, 12, 116, 39, 86, 245, 239, 63, 19, 112, 34, 11, 1, 157, 253, 87, 123, 86, 104, 106, 254, 148, 100, 122, 131, 41, 134, 2, 17, 0, 0, 0, 5, 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