Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a26ada48cd420d84dfb867b7b14753a8f9c483e5e82afef1ef3ad013fdf09a4

Tx prefix hash: 490a5664e60c106aae493ef0d84b8c8eeedff64d1787555dc971d8b36ab36f13
Tx public key: f917710a9e00bc16856aef4cdef44f2775011d6a342822e8d6cc4a2b7c7421f4
Timestamp: 1710885636 Timestamp [UCT]: 2024-03-19 22:00:36 Age [y:d:h:m:s]: 00:310:00:37:44
Block: 982009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221853 RingCT/type: yes/0
Extra: 01f917710a9e00bc16856aef4cdef44f2775011d6a342822e8d6cc4a2b7c7421f402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71e6eec7f29743dfcf409cd2a74437e2783f3afbdd40565aa361755728392711 0.600000000000 1442112 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": 982019, "vin": [ { "gen": { "height": 982009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71e6eec7f29743dfcf409cd2a74437e2783f3afbdd40565aa361755728392711" } } ], "extra": [ 1, 249, 23, 113, 10, 158, 0, 188, 22, 133, 106, 239, 76, 222, 244, 79, 39, 117, 1, 29, 106, 52, 40, 34, 232, 214, 204, 74, 43, 124, 116, 33, 244, 2, 17, 0, 0, 0, 6, 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