Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f17f170795a80b6cf77760e55cecea1f2e8699bb6aa6934aaca0b891cc98bf2

Tx prefix hash: 731f1761fdadebdcef4aaaafe4b5e8b2d8e85da43ede26b8eb65b40b559bb62c
Tx public key: c28a8d83a0c0fa7bb83df015de5157e55ba1eca401d655b9fd901f66d579caa8
Timestamp: 1711319329 Timestamp [UCT]: 2024-03-24 22:28:49 Age [y:d:h:m:s]: 01:239:01:25:39
Block: 985610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429541 RingCT/type: yes/0
Extra: 01c28a8d83a0c0fa7bb83df015de5157e55ba1eca401d655b9fd901f66d579caa80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04df6cf447b2d97d006b0834b6a5e571c73561ef8d1db57bd498a9cc95e4e389 0.600000000000 1445827 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": 985620, "vin": [ { "gen": { "height": 985610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04df6cf447b2d97d006b0834b6a5e571c73561ef8d1db57bd498a9cc95e4e389" } } ], "extra": [ 1, 194, 138, 141, 131, 160, 192, 250, 123, 184, 61, 240, 21, 222, 81, 87, 229, 91, 161, 236, 164, 1, 214, 85, 185, 253, 144, 31, 102, 213, 121, 202, 168, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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