Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0296238a2b09b60d84c8104676010c8b8a5a2fd5c444f8153a441fbb3f2fa36

Tx prefix hash: 102ce81e09b6dbb326df0eaf6f1293d4d0c2d5913255ba61ced9d40fb01b674d
Tx public key: d347c8e58d26397333cfa12f53caea0bff4121d9c2837355e42bd6f5263d8775
Timestamp: 1627573978 Timestamp [UCT]: 2021-07-29 15:52:58 Age [y:d:h:m:s]: 03:321:21:07:29
Block: 303249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1002293 RingCT/type: yes/0
Extra: 01d347c8e58d26397333cfa12f53caea0bff4121d9c2837355e42bd6f5263d87750211000000a3e6f80b5a000000000000000000

1 output(s) for total of 60.704121177000 dcy

stealth address amount amount idx
00: 5eb0d8ec57c05384de86f832b8775c0f4e173f092c2d0b231b5c9ae02935bc5a 60.704121177000 632970 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": 303259, "vin": [ { "gen": { "height": 303249 } } ], "vout": [ { "amount": 60704121177, "target": { "key": "5eb0d8ec57c05384de86f832b8775c0f4e173f092c2d0b231b5c9ae02935bc5a" } } ], "extra": [ 1, 211, 71, 200, 229, 141, 38, 57, 115, 51, 207, 161, 47, 83, 202, 234, 11, 255, 65, 33, 217, 194, 131, 115, 85, 228, 43, 214, 245, 38, 61, 135, 117, 2, 17, 0, 0, 0, 163, 230, 248, 11, 90, 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