Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5594cc41b6add424266fdaa337d2f8574e2d5b6bd333b7dca71b15752a922bd4

Tx prefix hash: 3bb5fd9f2fac5c6156636b167cb91e02d14ed7d8ddfd5de6bfae735604174417
Tx public key: 0f2b5ba6200b4313a8474e267bc2894e91b4f60dc70224527a1c1df7b549b154
Timestamp: 1725381641 Timestamp [UCT]: 2024-09-03 16:40:41 Age [y:d:h:m:s]: 00:088:13:24:35
Block: 1102172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63342 RingCT/type: yes/0
Extra: 010f2b5ba6200b4313a8474e267bc2894e91b4f60dc70224527a1c1df7b549b15402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aafdfbcc5672159c2382e6ade26b29dd52b40c8545b25e93d3164a9197bd3534 0.600000000000 1578503 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": 1102182, "vin": [ { "gen": { "height": 1102172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aafdfbcc5672159c2382e6ade26b29dd52b40c8545b25e93d3164a9197bd3534" } } ], "extra": [ 1, 15, 43, 91, 166, 32, 11, 67, 19, 168, 71, 78, 38, 123, 194, 137, 78, 145, 180, 246, 13, 199, 2, 36, 82, 122, 28, 29, 247, 181, 73, 177, 84, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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