Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 903c60c4bf6149f5b539a4d40daa6d947649f7c850c08f2243e29ac5dbed1c31

Tx prefix hash: 6ac82c2a1716e8b4f45da4b62db205ed9401ae8835b5b07c1c37252cf35a1a00
Tx public key: 792c68dfb9d9adb75ad904e5ab7c0b45d0d9c0f20e9fb8627aaaaade37c94a3d
Timestamp: 1684528204 Timestamp [UCT]: 2023-05-19 20:30:04 Age [y:d:h:m:s]: 02:172:08:33:54
Block: 763731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 642979 RingCT/type: yes/0
Extra: 01792c68dfb9d9adb75ad904e5ab7c0b45d0d9c0f20e9fb8627aaaaade37c94a3d021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.809455717000 dcy

stealth address amount amount idx
00: 99042acce0454c41a5d328f0fd755e84aef39f576594fa23578e1e743ec81122 1.809455717000 1212588 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": 763741, "vin": [ { "gen": { "height": 763731 } } ], "vout": [ { "amount": 1809455717, "target": { "key": "99042acce0454c41a5d328f0fd755e84aef39f576594fa23578e1e743ec81122" } } ], "extra": [ 1, 121, 44, 104, 223, 185, 217, 173, 183, 90, 217, 4, 229, 171, 124, 11, 69, 208, 217, 192, 242, 14, 159, 184, 98, 122, 170, 170, 222, 55, 201, 74, 61, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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