Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a394e8d37f8000bd3ed808f9a9648c43b28b1cd1ca8308e27673eceb906317d3

Tx prefix hash: d25b835d09ee4e7919fbcadc3626c2b133ac07e98d21cfd50222f435b4d20457
Tx public key: b276e74e47a270adcbea6cacaab997a26f20a84a15f662f967d2b68f86b55c9a
Timestamp: 1579014074 Timestamp [UCT]: 2020-01-14 15:01:14 Age [y:d:h:m:s]: 05:129:07:27:53
Block: 45368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242683 RingCT/type: yes/0
Extra: 01b276e74e47a270adcbea6cacaab997a26f20a84a15f662f967d2b68f86b55c9a021100000067391a8d0e000000000000000000

1 output(s) for total of 434.195496273000 dcy

stealth address amount amount idx
00: a4c8661ba1a8eb704fc3186277e3aca4c8fcf9296f368d453ccb37e267a9ea95 434.195496273000 82869 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": 45378, "vin": [ { "gen": { "height": 45368 } } ], "vout": [ { "amount": 434195496273, "target": { "key": "a4c8661ba1a8eb704fc3186277e3aca4c8fcf9296f368d453ccb37e267a9ea95" } } ], "extra": [ 1, 178, 118, 231, 78, 71, 162, 112, 173, 203, 234, 108, 172, 170, 185, 151, 162, 111, 32, 168, 74, 21, 246, 98, 249, 103, 210, 182, 143, 134, 181, 92, 154, 2, 17, 0, 0, 0, 103, 57, 26, 141, 14, 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