Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733e4b6d9dca4825b512dbcbf209828e8ae0dcd57e53d35cc12118fa988104f9

Tx prefix hash: 7c6fadba802c065a4b9643087b1c4e521c3219bf0b6b9633241d440063989546
Tx public key: 357b81bfdff76cd4b7951e3cb3307f6c414d7c6d64f97e5d5d38ea5e150b6820
Timestamp: 1577730928 Timestamp [UCT]: 2019-12-30 18:35:28 Age [y:d:h:m:s]: 05:055:13:33:02
Block: 35238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189405 RingCT/type: yes/0
Extra: 01357b81bfdff76cd4b7951e3cb3307f6c414d7c6d64f97e5d5d38ea5e150b68200211000000084943cd9f000000000000000000

1 output(s) for total of 469.075481050000 dcy

stealth address amount amount idx
00: 2555614e3c92f101f7ef1ebd2630b5937c70fc2e1ca953f6c3a44f1149e78ec4 469.075481050000 59340 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": 35248, "vin": [ { "gen": { "height": 35238 } } ], "vout": [ { "amount": 469075481050, "target": { "key": "2555614e3c92f101f7ef1ebd2630b5937c70fc2e1ca953f6c3a44f1149e78ec4" } } ], "extra": [ 1, 53, 123, 129, 191, 223, 247, 108, 212, 183, 149, 30, 60, 179, 48, 127, 108, 65, 77, 124, 109, 100, 249, 126, 93, 93, 56, 234, 94, 21, 11, 104, 32, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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