Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf44f7c93adf3f414d668a9c45798182e3c9aaf5efbf59f87b1130acb6edd700

Tx prefix hash: fd7148216c52626683576420e3aefc049eed54a8def84468215ee6fea4840485
Tx public key: e41a28cc15602a70cb9d94c50f0aa504dba9ca4d9171712507511ec888c8c724
Timestamp: 1715268127 Timestamp [UCT]: 2024-05-09 15:22:07 Age [y:d:h:m:s]: 00:331:16:57:28
Block: 1018326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237107 RingCT/type: yes/0
Extra: 01e41a28cc15602a70cb9d94c50f0aa504dba9ca4d9171712507511ec888c8c72402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 962cef6ec0f8defb90592273fd812d8e41b2934326cb7f520c2fa01c6c4ee9f0 0.600000000000 1482115 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": 1018336, "vin": [ { "gen": { "height": 1018326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "962cef6ec0f8defb90592273fd812d8e41b2934326cb7f520c2fa01c6c4ee9f0" } } ], "extra": [ 1, 228, 26, 40, 204, 21, 96, 42, 112, 203, 157, 148, 197, 15, 10, 165, 4, 219, 169, 202, 77, 145, 113, 113, 37, 7, 81, 30, 200, 136, 200, 199, 36, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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