Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf9698fc963292997c0d3be7cfbe5bb99cf02e56722bb60cd79296a03e340a2e

Tx prefix hash: 8d00db6cd1ba526eab6e9143313c679c5a7f6c59d7b879777d5a01bfdbd62354
Tx public key: fee5e50e54de2d94de99f376083bdf50e398a8344adbcbf7d0aad00ac4ac1a67
Timestamp: 1695522769 Timestamp [UCT]: 2023-09-24 02:32:49 Age [y:d:h:m:s]: 01:215:16:32:32
Block: 854820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415248 RingCT/type: yes/0
Extra: 01fee5e50e54de2d94de99f376083bdf50e398a8344adbcbf7d0aad00ac4ac1a670211000000084b8f5122000000000000000000

1 output(s) for total of 0.902872732000 dcy

stealth address amount amount idx
00: aa06feac6acd4dc26f145b6185f0cc6f6926f9d08c5aa8757d364f622d73400b 0.902872732000 1308812 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": 854830, "vin": [ { "gen": { "height": 854820 } } ], "vout": [ { "amount": 902872732, "target": { "key": "aa06feac6acd4dc26f145b6185f0cc6f6926f9d08c5aa8757d364f622d73400b" } } ], "extra": [ 1, 254, 229, 229, 14, 84, 222, 45, 148, 222, 153, 243, 118, 8, 59, 223, 80, 227, 152, 168, 52, 74, 219, 203, 247, 208, 170, 208, 10, 196, 172, 26, 103, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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