Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3568cb78cffbbe7a1f95d89dd2d0151e7f8f42ef9c1bd2b78e7a1fc5bc60f665

Tx prefix hash: 7d71aa2078d15414d41a78d37c209abae04a50b7307ddaebc7bd7b6238eabd0f
Tx public key: de879cabeee55701597cdc3158c1f0a171b5a5bf0a240ce7d2ed1e55cc116b1b
Timestamp: 1722758248 Timestamp [UCT]: 2024-08-04 07:57:28 Age [y:d:h:m:s]: 00:246:13:13:06
Block: 1080415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176093 RingCT/type: yes/0
Extra: 01de879cabeee55701597cdc3158c1f0a171b5a5bf0a240ce7d2ed1e55cc116b1b021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccce8ad69549b68cb03d510955a7b0bec5c6d16530f2c4c28380eb33d0cfd725 0.600000000000 1553762 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": 1080425, "vin": [ { "gen": { "height": 1080415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccce8ad69549b68cb03d510955a7b0bec5c6d16530f2c4c28380eb33d0cfd725" } } ], "extra": [ 1, 222, 135, 156, 171, 238, 229, 87, 1, 89, 124, 220, 49, 88, 193, 240, 161, 113, 181, 165, 191, 10, 36, 12, 231, 210, 237, 30, 85, 204, 17, 107, 27, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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