Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d93db27d093abf16a4bf4b9a1e5dcba8292aacef3f84584657d7e121f20d43b

Tx prefix hash: 0033c1efb377284bdde0edb6e3298b093881f36969370c16d15a1c7969cbb979
Tx public key: 89622562aadc9d43ca327d3e6d090566e4765920aec2eed5bdd0ad93ce4ac2b4
Timestamp: 1733272675 Timestamp [UCT]: 2024-12-04 00:37:55 Age [y:d:h:m:s]: 00:115:10:28:11
Block: 1167492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82303 RingCT/type: yes/0
Extra: 0189622562aadc9d43ca327d3e6d090566e4765920aec2eed5bdd0ad93ce4ac2b40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4687ba45581e3eb2f6300861e8c55816bae3a0fb25defbae8e0e496e9a607c7 0.600000000000 1653189 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": 1167502, "vin": [ { "gen": { "height": 1167492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4687ba45581e3eb2f6300861e8c55816bae3a0fb25defbae8e0e496e9a607c7" } } ], "extra": [ 1, 137, 98, 37, 98, 170, 220, 157, 67, 202, 50, 125, 62, 109, 9, 5, 102, 228, 118, 89, 32, 174, 194, 238, 213, 189, 208, 173, 147, 206, 74, 194, 180, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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