Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a549e48b2c477642257627016110fee475c7e361095fb3151716ca7382c7c00d

Tx prefix hash: c7bcc1bb15acc33bf265e3ad508c8b5f2e52b3883e53e1375e865236b1e2ca06
Tx public key: f8f57d80f74fb42851d6c9b588d38d95a8560eddae8b25224829bd10046acca5
Timestamp: 1636593079 Timestamp [UCT]: 2021-11-11 01:11:19 Age [y:d:h:m:s]: 03:220:09:56:01
Block: 371770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 935844 RingCT/type: yes/0
Extra: 01f8f57d80f74fb42851d6c9b588d38d95a8560eddae8b25224829bd10046acca502110000000c4a0f5013000000000000000000

1 output(s) for total of 35.989188378000 dcy

stealth address amount amount idx
00: 1db7b5a33c31ad4160e756a8e3449e1d47ed49761bb31dd786739faaa640e83b 35.989188378000 753278 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": 371780, "vin": [ { "gen": { "height": 371770 } } ], "vout": [ { "amount": 35989188378, "target": { "key": "1db7b5a33c31ad4160e756a8e3449e1d47ed49761bb31dd786739faaa640e83b" } } ], "extra": [ 1, 248, 245, 125, 128, 247, 79, 180, 40, 81, 214, 201, 181, 136, 211, 141, 149, 168, 86, 14, 221, 174, 139, 37, 34, 72, 41, 189, 16, 4, 106, 204, 165, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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