Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d983c8f4ab8c722d1e4132612d804f7ccae6f5babbbc810651a796729c968681

Tx prefix hash: ad16c46381b92f5587a961420f3d8b67b5493e08e23f23e57e0ff8fc55a736c3
Tx public key: c6305630911b42a4b2cbbab8d4d327f9f3c651a9e6acc7e5a818939683a43cb6
Timestamp: 1660843606 Timestamp [UCT]: 2022-08-18 17:26:46 Age [y:d:h:m:s]: 02:270:23:27:18
Block: 568666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714917 RingCT/type: yes/0
Extra: 01c6305630911b42a4b2cbbab8d4d327f9f3c651a9e6acc7e5a818939683a43cb602110000000333af99f4000000000000000000

1 output(s) for total of 8.012602209000 dcy

stealth address amount amount idx
00: c6dfaf3a1af707f0670be48ace5fa52f0f9410b96b410125ff959a2a9bcb0046 8.012602209000 1001793 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": 568676, "vin": [ { "gen": { "height": 568666 } } ], "vout": [ { "amount": 8012602209, "target": { "key": "c6dfaf3a1af707f0670be48ace5fa52f0f9410b96b410125ff959a2a9bcb0046" } } ], "extra": [ 1, 198, 48, 86, 48, 145, 27, 66, 164, 178, 203, 186, 184, 212, 211, 39, 249, 243, 198, 81, 169, 230, 172, 199, 229, 168, 24, 147, 150, 131, 164, 60, 182, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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