Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a395c4d162b98e4e2a0497986d9b1cada732a091965bd641a21a57b7e22fbf

Tx prefix hash: 99a336182dc8b2188a182dc7c4488a855a06001b59d621baf02dae437d0e3be5
Tx public key: c4184e45a898f3f522d681a0fadeefe2e891c1cee14ab6d97e75b2f2ae31366e
Timestamp: 1659112309 Timestamp [UCT]: 2022-07-29 16:31:49 Age [y:d:h:m:s]: 02:252:12:00:20
Block: 554370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701650 RingCT/type: yes/0
Extra: 01c4184e45a898f3f522d681a0fadeefe2e891c1cee14ab6d97e75b2f2ae31366e021100000001e6d27f9c000000000000000000

1 output(s) for total of 8.935979956000 dcy

stealth address amount amount idx
00: 404d4160fdf4e9d81e24182607995082fc8605b29167dc645e01facb7af4c62c 8.935979956000 986220 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": 554380, "vin": [ { "gen": { "height": 554370 } } ], "vout": [ { "amount": 8935979956, "target": { "key": "404d4160fdf4e9d81e24182607995082fc8605b29167dc645e01facb7af4c62c" } } ], "extra": [ 1, 196, 24, 78, 69, 168, 152, 243, 245, 34, 214, 129, 160, 250, 222, 239, 226, 232, 145, 193, 206, 225, 74, 182, 217, 126, 117, 178, 242, 174, 49, 54, 110, 2, 17, 0, 0, 0, 1, 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