Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f314af50f661235f258e0a7fe144faf235b493a8f244897aab1b4f074a5b66

Tx prefix hash: 7a2b4de330017669177d7f9e8bef09a1425772dadfcf58e6494260f58d6c435f
Tx public key: 775da526b28ba69e72cd6574d16238ce6480d6df9ec34bd1b8408bf8d7ea1629
Timestamp: 1736425369 Timestamp [UCT]: 2025-01-09 12:22:49 Age [y:d:h:m:s]: 00:159:23:55:28
Block: 1193595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114058 RingCT/type: yes/0
Extra: 01775da526b28ba69e72cd6574d16238ce6480d6df9ec34bd1b8408bf8d7ea16290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c80e5d28329fe1a91f95c623c1fcf35d61522faacae60f96a3a867a1549380c9 0.600000000000 1680158 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": 1193605, "vin": [ { "gen": { "height": 1193595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80e5d28329fe1a91f95c623c1fcf35d61522faacae60f96a3a867a1549380c9" } } ], "extra": [ 1, 119, 93, 165, 38, 178, 139, 166, 158, 114, 205, 101, 116, 209, 98, 56, 206, 100, 128, 214, 223, 158, 195, 75, 209, 184, 64, 139, 248, 215, 234, 22, 41, 2, 17, 0, 0, 0, 5, 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