Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6a19271f6bdd21056ee446d899d3f002843c33adc3046504acb85a29a68b04

Tx prefix hash: c5955d63ed1166a93812222c10ecb47914f82ff68c2d52539367fb5e4d6c45fa
Tx public key: 9060e77a32f182fd79e88f725851451e6e07bdd4295901f3f79b6e6a82bfc4b3
Timestamp: 1714220541 Timestamp [UCT]: 2024-04-27 12:22:21 Age [y:d:h:m:s]: 00:307:14:11:07
Block: 1009641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219853 RingCT/type: yes/0
Extra: 019060e77a32f182fd79e88f725851451e6e07bdd4295901f3f79b6e6a82bfc4b30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ad4fbe0e148324e436c6b6132b0b93b9f918bfbe1834433b285f668fe96ba81 0.600000000000 1471373 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": 1009651, "vin": [ { "gen": { "height": 1009641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad4fbe0e148324e436c6b6132b0b93b9f918bfbe1834433b285f668fe96ba81" } } ], "extra": [ 1, 144, 96, 231, 122, 50, 241, 130, 253, 121, 232, 143, 114, 88, 81, 69, 30, 110, 7, 189, 212, 41, 89, 1, 243, 247, 155, 110, 106, 130, 191, 196, 179, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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