Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc3a9e37fd3aee1e722445a90487cd1d16a1bac16dfeb08b3d43a2ee25b6e0a

Tx prefix hash: ca2eef1e3f8ed52eaa905096fe21c136b6d9f156cfb20d1fc4d0e34202e1d19f
Tx public key: 0f963890c8da7c763315d2bb1c0b01b4dde739f1784fe5ef7fe09ea461499c08
Timestamp: 1735990381 Timestamp [UCT]: 2025-01-04 11:33:01 Age [y:d:h:m:s]: 00:111:00:27:37
Block: 1190001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79135 RingCT/type: yes/0
Extra: 010f963890c8da7c763315d2bb1c0b01b4dde739f1784fe5ef7fe09ea461499c0802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6b867ab3526aec91022640046068e3958b001633026109dfa40186adb45685 0.600000000000 1676516 of 15

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": 1190011, "vin": [ { "gen": { "height": 1190001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6b867ab3526aec91022640046068e3958b001633026109dfa40186adb45685" } } ], "extra": [ 1, 15, 150, 56, 144, 200, 218, 124, 118, 51, 21, 210, 187, 28, 11, 1, 180, 221, 231, 57, 241, 120, 79, 229, 239, 127, 224, 158, 164, 97, 73, 156, 8, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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