Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c66bd7ea3ac377f9a8497d0f4780cf32070967e727fd11f57d88556a481415a3

Tx prefix hash: 94facec9217a4db299454bb298699df574b1ed7f99a9201e98ae578d591b51db
Tx public key: 92cc643e5f5c835ad5d9b6b1c2aa1a68f0362497e0e241a810bed42bc7cdba60
Timestamp: 1736585788 Timestamp [UCT]: 2025-01-11 08:56:28 Age [y:d:h:m:s]: 00:080:21:03:23
Block: 1194924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57564 RingCT/type: yes/0
Extra: 0192cc643e5f5c835ad5d9b6b1c2aa1a68f0362497e0e241a810bed42bc7cdba60021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 476682ea703a3c435513ee83c7070a3a5e64ba104cdeb94dfbbe07fac434dc77 0.600000000000 1681503 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": 1194934, "vin": [ { "gen": { "height": 1194924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "476682ea703a3c435513ee83c7070a3a5e64ba104cdeb94dfbbe07fac434dc77" } } ], "extra": [ 1, 146, 204, 100, 62, 95, 92, 131, 90, 213, 217, 182, 177, 194, 170, 26, 104, 240, 54, 36, 151, 224, 226, 65, 168, 16, 190, 212, 43, 199, 205, 186, 96, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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