Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: affa481b9662cba37adbe92c1d2c0b05b17b4010c511ad6aad4fe5dcb397a2bb

Tx prefix hash: 007a56efd36a6ed289649573b8afffd9ffba78c62a77b895c4c2a616d94bcd7e
Tx public key: 3d8d5b66fec40a425149a34a10ff7a051e24dafc951055cc69f3375703e6f808
Timestamp: 1704740640 Timestamp [UCT]: 2024-01-08 19:04:00 Age [y:d:h:m:s]: 01:328:15:50:37
Block: 931037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493755 RingCT/type: yes/0
Extra: 013d8d5b66fec40a425149a34a10ff7a051e24dafc951055cc69f3375703e6f80802110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e300214d0c99b8be90d68d58f25fd9fe247911074a0880d7003f78fee63d0cb2 0.600000000000 1388929 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": 931047, "vin": [ { "gen": { "height": 931037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e300214d0c99b8be90d68d58f25fd9fe247911074a0880d7003f78fee63d0cb2" } } ], "extra": [ 1, 61, 141, 91, 102, 254, 196, 10, 66, 81, 73, 163, 74, 16, 255, 122, 5, 30, 36, 218, 252, 149, 16, 85, 204, 105, 243, 55, 87, 3, 230, 248, 8, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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