Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed537f184ef09009bac1e22730ce2ece2d546023cfb99d4e9528de0b88ef4eb

Tx prefix hash: c97e85ddb138b08218f43e61f2a1fb7d27150a3090bec6a49bb65a3dc929544c
Tx public key: 07610d5291a3ea2f6cdc76971f638c57296d382164169f60bd97388df42be29c
Timestamp: 1705696083 Timestamp [UCT]: 2024-01-19 20:28:03 Age [y:d:h:m:s]: 01:086:05:16:46
Block: 938942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322727 RingCT/type: yes/0
Extra: 0107610d5291a3ea2f6cdc76971f638c57296d382164169f60bd97388df42be29c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ff6adffcafb4df6f1de7dc9de0d1f5640df6434938bb6ded7232f059abf8cb 0.600000000000 1397026 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": 938952, "vin": [ { "gen": { "height": 938942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ff6adffcafb4df6f1de7dc9de0d1f5640df6434938bb6ded7232f059abf8cb" } } ], "extra": [ 1, 7, 97, 13, 82, 145, 163, 234, 47, 108, 220, 118, 151, 31, 99, 140, 87, 41, 109, 56, 33, 100, 22, 159, 96, 189, 151, 56, 141, 244, 43, 226, 156, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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