Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1c605990bc28c0feee3ccf1274767253dc2650aa3ff098d46ed93dd2571f40

Tx prefix hash: 45fcbe83dd0aa7df025c6669a5b56a4f3addc18a58a0be1ed361ae75264c0aa8
Tx public key: 344cab1a25af07eb8e7d99866c47cfeffff723c4a5d3a0ceb3de94483fedd62d
Timestamp: 1712879441 Timestamp [UCT]: 2024-04-11 23:50:41 Age [y:d:h:m:s]: 01:013:01:46:43
Block: 998498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270325 RingCT/type: yes/0
Extra: 01344cab1a25af07eb8e7d99866c47cfeffff723c4a5d3a0ceb3de94483fedd62d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abf4d8f8d24e34b80711a1b697c41449ecbfe8921458d76e55837a7c40684d11 0.600000000000 1458950 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": 998508, "vin": [ { "gen": { "height": 998498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abf4d8f8d24e34b80711a1b697c41449ecbfe8921458d76e55837a7c40684d11" } } ], "extra": [ 1, 52, 76, 171, 26, 37, 175, 7, 235, 142, 125, 153, 134, 108, 71, 207, 239, 255, 247, 35, 196, 165, 211, 160, 206, 179, 222, 148, 72, 63, 237, 214, 45, 2, 17, 0, 0, 0, 6, 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