Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c1738cf74eae1915511808f509577d8717308ddb0b69b2a198e4a16d974ab25

Tx prefix hash: a2f2df3338a264b46b3cc1b07f571f6e0dd9dab5d0ec84704ff2b0998c232e48
Tx public key: 7614d6dd863dc0f8d207c3e81cefc718054d55b563dd964a415b1a0afad44de6
Timestamp: 1756633243 Timestamp [UCT]: 2025-08-31 09:40:43 Age [y:d:h:m:s]: 00:130:11:01:01
Block: 1358276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93302 RingCT/type: yes/0
Extra: 017614d6dd863dc0f8d207c3e81cefc718054d55b563dd964a415b1a0afad44de6021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c0a3ae4ee7ed3f70e8fba488cee083f08e7ae8707f2a3e583bdab84f9411a34 0.600000000000 1846289 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": 1358286, "vin": [ { "gen": { "height": 1358276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0a3ae4ee7ed3f70e8fba488cee083f08e7ae8707f2a3e583bdab84f9411a34" } } ], "extra": [ 1, 118, 20, 214, 221, 134, 61, 192, 248, 210, 7, 195, 232, 28, 239, 199, 24, 5, 77, 85, 181, 99, 221, 150, 74, 65, 91, 26, 10, 250, 212, 77, 230, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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