Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b969825fd26cfa1c5567d6cbd7cf940fbc63419ab91a295401fec254c52b9dfd

Tx prefix hash: 0405dae3af7fdde26f1ac4efc521375586e90e6f519a2ba03394624c7cc08e06
Tx public key: f3a9b4c6e98c8c3c5c695d258f97f568335fcf027a8afff5b6248ae6aaaa4fa5
Timestamp: 1695386287 Timestamp [UCT]: 2023-09-22 12:38:07 Age [y:d:h:m:s]: 01:184:07:13:48
Block: 853694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392775 RingCT/type: yes/0
Extra: 01f3a9b4c6e98c8c3c5c695d258f97f568335fcf027a8afff5b6248ae6aaaa4fa5021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.910662481000 dcy

stealth address amount amount idx
00: ec28eac3e44e1baf609dc2720a98679796d62360aff3c42061c896f30bdbc962 0.910662481000 1307624 of 0

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": 853704, "vin": [ { "gen": { "height": 853694 } } ], "vout": [ { "amount": 910662481, "target": { "key": "ec28eac3e44e1baf609dc2720a98679796d62360aff3c42061c896f30bdbc962" } } ], "extra": [ 1, 243, 169, 180, 198, 233, 140, 140, 60, 92, 105, 93, 37, 143, 151, 245, 104, 51, 95, 207, 2, 122, 138, 255, 245, 182, 36, 138, 230, 170, 170, 79, 165, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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